Skip to content

fix(rust/signed-doc): Apply new DocType #347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 21 commits into from
May 29, 2025

Conversation

bkioshn
Copy link
Contributor

@bkioshn bkioshn commented May 26, 2025

Description

Apply new DocType to existing type field

Related Issue(s)

Closes #328

Breaking Changes

There shouldn't be any breaking change since it should be backward compatible.

Related Pull Requests

#339

Please confirm the following checks

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream module

@bkioshn bkioshn self-assigned this May 26, 2025
@bkioshn bkioshn added the enhancement New feature or request label May 26, 2025
@bkioshn bkioshn added this to Catalyst May 26, 2025
@bkioshn bkioshn changed the title Fix/apply new doc type fix(rust/signed_doc): Apply new DocType May 27, 2025
@bkioshn bkioshn changed the title fix(rust/signed_doc): Apply new DocType fix(rust/signed-doc): Apply new DocType May 27, 2025
@bkioshn bkioshn marked this pull request as ready for review May 27, 2025 12:45
@bkioshn bkioshn added the review me PR is ready for review label May 27, 2025
@bkioshn bkioshn moved this from New to 👀 In review in Catalyst May 27, 2025
@bkioshn bkioshn removed the review me PR is ready for review label May 27, 2025
Copy link
Contributor

github-actions bot commented May 27, 2025

Test Report | ${\color{lightgreen}Pass: 336/336}$ | ${\color{red}Fail: 0/336}$ |

@bkioshn bkioshn added the review me PR is ready for review label May 27, 2025
Copy link
Contributor

@Mr-Leshiy Mr-Leshiy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also could you update proposal.rs, comment.rs and submission.rs tests with applying new doc type ids and also remain at least one test case with the old types.
e.g.
for the proposal.rs inside test_valid_proposal_doc, test_valid_proposal_doc_with_empty_provider and test_invalid_proposal_doc update "type" field definition to the new one (as array with multiple values), and also add one more new test test_valid_proposal_doc_old_type with preserving current test case with the old type definition.
(the same thing do for the comment.rs and submission.rs)

@github-project-automation github-project-automation bot moved this from 👀 In review to 🔖 Ready in Catalyst May 28, 2025
@bkioshn bkioshn requested a review from Mr-Leshiy May 29, 2025 04:04
@bkioshn bkioshn merged commit b5f12bb into feat/new-cat-signed-doc May 29, 2025
24 checks passed
@bkioshn bkioshn deleted the fix/apply-new-doc-type branch May 29, 2025 06:37
@github-project-automation github-project-automation bot moved this from 🔖 Ready to ✅ Done in Catalyst May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request review me PR is ready for review
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants